[ci] Use VM for PR license check on Buildkite #15428
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This commit switches the license check to be run using a VM (as its currently done in Jenkins) due to the problem described in elastic#15427. This is a bit unfortunate because the Jenkins workflow builds a Docker image (based on Ubuntu 18.04) within the VM and then runs the check inside a container. We will address this issue and remove this unnecessary VM -> build docker image -> run inside Docker in a future PR.
|
SonarQube Quality Gate
|
|
This is not needed, containers work fine, the problem was related to #15427 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Release notes
[rn:skip]
What does this PR do?
This commit switches the license check to be run using a VM (as its currently done in Jenkins) due to the problem described in #15427.
This is a bit unfortunate because the Jenkins workflow builds a Docker image (based on Ubuntu 18.04) within the VM and then runs the check inside a container. We will address this issue and remove this unnecessary VM -> build docker image -> run inside Docker in a future PR.
Related issues
#15427.